-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-52142][SQL] Display table constraints in SHOW CREATE TABLE COMMAND #51541
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| name, | ||
| definition(), | ||
| enforced ? "ENFORCED" : "NOT ENFORCED", | ||
| validationStatus, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @aokolnychyi
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my understanding, where can we see the status after this, @gengliangwang ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. We have to remove it since the validation status is not supported in the parser.
We can still display it in the "DESC TABLE" command
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM if DESC TABLE serves the purpose. Thank you, @gengliangwang .
cc @peter-toth
|
There seem to be some relevant test failures in the logs. @gengliangwang , can you please take a look those? |
|
@dongjoon-hyun @peter-toth Thanks for the review, merging to master |
What changes were proposed in this pull request?
Display table constraints in the SHOW CREATE TABLE COMMAND
Why are the changes needed?
Displaying table constraints is expected for the SHOW CREATE TABLE COMMAND
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit test
Was this patch authored or co-authored using generative AI tooling?
No